Agile Business Analysts? I have recently been fleshing out my thoughts on the role of business analysts in an Agile team. This is something I have historically addressed on a case-by-case basis with clients, but when thinking about it last week at a client site, I realized that I do have a general take on how the role and responsibilities of a business analyst change when a group moves to using an Agile process. Per the usual, I ll be using Scrum as the example process where needed. The Classical Roles Historically the business analyst has had two primary roles. In a process where cross-functional communication and collaboration are minimized, these roles are essential. What little communication that takes place between the business and the software development teams purporting to serve them passes almost exclusively through one or more business analysts. I view the business analyst in a phased development approach as having two roles; Translator and Gatekeeper. The Translator The business analyst is primarily tasked with taking the needs of the business and translating them into a written document that is then handed to the software developers and testers. This role s necessity is based upon some fundamental assumptions. First, programmers and testers are on the whole, too socially retarded to actually talk to the business persons and find out what they want. Second, the business is primarily viewed as being unable to focus its thought long enough to tell the programmers and testers what they need. Since a key value of an Agile approach to software development is to have individuals and their interactions be the driving force rather than processes an tools (see The Agile Manifesto), the obliteration of this role is a primary objective. The Gatekeeper Business analysts are also viewed the gatekeepers for requirements in classical, phased software process approaches. This is a somewhat unfair role, since they rarely have the authority to prevent business or technology changes, like a meter maid trying to stop an armed terrorist. It s even more unnatural since change always happens, so it s like the meter maid being assigned to an anti-terrorist unit with no additional training, authority, or weapons. The Agile Roles Some of the more extreme practitioners of Agile methodologies say that business analysts have no role in an Agile team. I disagree, provided the role of the business analyst is allowed to evolve. The roles I ve seen them take on as valuable members of an Agile team are Facilitator, Historian, and Journalist. The Facilitator A high degree of collaboration and interaction take place between business and technology in Agile Software Development. The business analyst can serve a critical need in these interactions, facilitating communication between business and technology and making sure that critical areas are being covered in an interaction. This can be a more fulfilling experience for an analyst, since they often talk to one side, then go to other to pass on the information, all the while thinking, Man, this would be simpler if you were both in the room with me at the same time. The Historian The business analyst s documentation skill is excellent for capturing significant information that often gets lost in a team of purely technical people. I have seen some great uses of business analysts in this area. One is to document the system that the team actually builds (not the big, up-front imagined system that is covered in a phased design stage). Another is capturing key technological and architectural decisions and the context in which they were made, so that when a group revisits certain items asking, Why in the world did we decide to do that? , they have the means to be reminded or informed why a particular path was chosen. The Journalist The business analyst can also be the team s journalist, making sure the latest information makes it out to all interested parties. One creative approach I ve seen at a client site is a business analyst who has a project blog. He posts entries after each meeting between the business and technology, documenting what new user stories were created (even scans in the story cards!), a summary of the discussions held, and documents any key decisions that might have been made. Oh, and he provides an excellent executive summary at the top that s suitable for anyone s review, right up to the CEO. Tell me you wouldn t love to have that guy in your Agile team.

So I finally got around to checking out the TED site; I ve quickly become a fan. One of the first talks I watched was Steven Levitt s child carseats talk. Both the talk and the feedback comments on the TED site reminded me of things I see in software development. Here s the video if you haven t seen it. Steven Levitt shows in his talk how 30 years of data on car crash fatalities imply that carseats do not outperform regular seatbelts for children ages 2 and up. Anyone who has a child or grandchildren will probably bristle at hearing that; as the father of a pre-schooler, it certainly gave me pause. We spent no small amount of time and decent chunk of money in selecting carseats for our child, thinking we had done our best to ensure our child s safety. For that matter, it would be illegal for us not to have done so. To see a decent-sized data sample suggesting my child would be better off in a seatbelt at her age is rather unsettling. By the end of the talk, I took away these observations:

• This great swath of an initiative was started by a very small yet vocal group of proponents whose assertions received little scrutiny.
• A solution tailored to the specific constraints of a portion of the audience has been put forth as the de facto solution for the entire audience.
• There is an ongoing assumption that the more complicated and costly solution must be superior to the simpler, existing solution.
• Cursory evaluation of a data set without rigorous attention to mitigating factors can lead to wildly inaccurate conclusions.
• The acceptability of a given solution is often tested against a narrow band of the overall criteria, and the solution is often optimized to pass that test.
• The likelihood that people will continue to choose the more expensive and complicated solution despite any data is high.

So, software professionals, does any of that sound familiar? It reminds me of numerous initiatives over the years that have led us inexorably to the software productivity morass we have slogged through for years now. I suppose the most heinous case study in my own experience would be J2EE and the insistence that it was the solution that any reasonable business application would choose for a platform. (Before you .Net folks jump on that one, DCOM and later the .Net enterprise stack was much the same.) And who hasn t read a benchmark or white paper with seemingly incontrovertible data depicted in highly-polished graphics insisting that Product Y is the one solution to address them all? I noticed that there were comments below the video on its page at the TED site, largely because the negative verbiage of the topmost comment jumped out at me. I took the time to read through them all (there were 36 at the time of this writing), and to my amusement, I saw parallels between them and how people react to questioning and examining our existing practices and means of developing software. See if any of these strike a chord:

• The idea that what we re doing might be wrong unsettles some people, and their response is often ferocious and irrational defense of the status quo.
• Those who have a financial stake in the current mode of operation are less likely to be open to scrutinizing it.
• There will be some people whose primary objection to the scrutiny is that they didn t think of doing it first; these people will sometimes attack the person questioning things on the grounds that it s all a selfish, attention-mongering endeavor.
• There are some people who will also be open to examining why and how we re doing things; whether they conclude the same thing or not, they are a welcome presence among the larger mass of those who ardently refuse to entertain the possibility of a need to change.

In recent years I ve been greatly encouraged by the willingness of companies to question whether or not the heavyweight frameworks and technology stacks are what they should be using. Helping companies slough off high-ceremony processes in favor of right-sized process that focuses on delivering the right software in a timely manner has been some of the more rewarding work I ve done the past several years. I think we have an encouraging number of people in the industry who are challenging the more expensive and complicated always equals better mantra. For the brave individuals willing to put these questions to the community at large, I hope you find some comfort in knowing that the resistance and rejection you will encounter is a thing to be expected; you are not alone in that respect. Here s hoping we continue to be open to self-examination, no matter what emotional responses it might provoke or what fear of the future it may stir up within us.

Then they stopped, and Thorin muttered something about supper, and where shall we get a dry patch to sleep on? Not until then did they notice Gandalf was missing. So far he had come all the way with them, never saying if he was in the adventure or merely keeping them company for a while. He had eaten most, talked most, and laughed most. But now he simply was not there at all! Just when a wizard would have been most useful, too, groaned Dori and Nori (who shared the hobbit s views about regular meals, plenty and often).

- J.R.R. Tokien, The Hobbit

I am very fond of the works of J.R.R. Tolkien; it would not surprise me to find that many of you recognize these words from the second chapter of The Hobbit titled Roast Mutton . It occurred to me recently that there are parallels between Gandalf s role in The Hobbit and that of an Agile coach. Now, before my fellow Tolkien enthusiasts leap on their keyboards, bear with me on this. Know that I am not saying an Agile coach is on par with a wizard (OK, with one of the Istari sent by the Valar, but let s table that so as not to scare off the normal folk, alright?); that should be enough to calm you down. In the excerpt from The Hobbit at the top of the page, Bilbo and the dwarves have run into their first predicament. Note that it s not a particularly difficult situation; they just need to find shelter and partake of some food. Fire would be nice, too, if it could be managed. (Mind you, it s the first day of their journey; they set off mere hours ago fully provisioned and riding on ponies.) It isn t very long before the fledgling group finds itself not only without shelter and food, but in the hands of three rather nasty trolls who are deciding how best to eat the entire group. Gandalf returns once things have gotten out of control, and with some subtle adjustments to the situation, the crisis is averted. Could Gandalf have come back sooner and spared them this entire experience? Perhaps, but in their struggle a few key things happened. First, the group had to work out how to assess tasks at hand and appropriately delegate. To their credit, that effort was partially successful. The most skilled firestarters were assigned to that task, one of the keen-eyed dwarves was assigned to be the lookout. Second, they gathered some field experience that led to the establishment of improved practices, i.e. don t leave the ponies laden with packs when you make camp, particularly if it s all your food. (They lost most of their food that night when the pony carrying it bolted and ran straight into a nearby river later that night.) Third, Bilbo Baggins was called upon to perform his first task as burglar, albeit a fool s errand that landed them in the troll predicament. While Bilbo was wildly under-equipped for his job, he managed to work through it. That experience began a developmental journey that would prepare him for the great things that would be expected of him later on. This was not Gandalf s first adventure, nor was it the first group of people he needed to equip and challenge in order to develop them to a point that they could accomplish their goal. At this point, he s been in Middle-Earth just shy of 2,000 years. He would have been more than capable of walking them through their entire journey, but to what end? Agile coaching is a discipline that aims to help teams develop their own use of methodologies like Scrum and cross-methodology practices like testing, user stories, etc. This means equipping teams with just enough information to strike out on their own for a bit, then letting them run with it rather than dazzle them with one s own mastery so as to appear like the indispensable demigod. Until people struggle with the terse maxims of Agile Software Development, they cannot internalize them. And when the wizard is always around, why bother struggling? One of my greatest frustrations as an Agile coach is how few companies are willing to take a coaching approach with their Agile adoption. They want you to come in and be the demigod as a full-time contractor. Sure, there are fiscal, political, and seemingly practical reasons that they will cite; I chalk most of them up to being excuses for a lack of willingness to embrace what it would take to face the hard task of nurturing what you have. It s seemingly easier to just throw more money at more bodies and hope that somehow things will all work out, and surely if you can stumble upon some superstar to wrangle the mess, you ll eventually be able to browbeat them into becoming a full-time employee. Don t get me wrong; in some ways, I benefit from this dysfunction. From a selfish business standpoint, having a single full-time client is certainly easier than juggling multiple concurrent clients and their schedules. As far as actually accomplishing the aim of my business, however, I think it hinders the mission. One of my aims in working with companies is to be a coach despite being brought in as a contractor. It s certainly possible, though it is more challenging. There s not that natural separation of the coach from the team that forces them to take up the mantle on their own. Few things in my work are more rewarding than having a developer come to me and say, I wasn t really sure this Agile stuff could work, but now, after going through all this, I wouldn t want to go back to the old way of doing things. Much later in the journey of the hobbit and his dwarf companions, Bilbo is again called upon for a challenging task. His response makes me think Gandalf s approach has worked:

Perhaps I have begun to trust my luck more than I used to in the old days he meant last spring before he left his own house, but it seemed centuries ago but anyway I think I will go and have a peep at once and get it over. Now who is coming with me?

- J.R.R. Tokien, The Hobbit

Here s hoping more people will be willing to embrace the challenging, messy, and altogether beneficial task of equipping teams and allowing them to struggle when necessary, even if it means the occasional scuffle with trolls.

I received my author copy of 97 Things Every Software Architect Should Know in the mail yesterday, which means it should be hitting shelves in bookstores soon. I contributed 2 of the 97 things, so I m now published in some manner of speaking. You can see the book (yes, that s me in the top left of the group of face shots) here.

Opensync updates Some time ago, Opensync-0.38 got released, and it is now available in experimental. The evolution-data-server and the Opie plugins are now available again, as well as the new tomboy (in NEW) and a rewritten google-calendar/contacts plugin. The google plugin requires the new libgcal, which I have just uploaded to NEW. Unfortunately, kitchensync is still not ported to latest Opensync-0.3x (and got dropped for KDE4.2), so one still needs to use the command-line msynctool program. Also not ported are the (KDE3) kdepim and the currently under development Akonadi plugin. Other important plugins missing for 0.38 are the Windows Mobile, Blackberry, Palm and IRMC plugins. I tried to suggest making 0.38.x point releases including more ported plugins, but it seems development is turning towards 0.39 already, and yet some more API changes were done, this time mostly removing unnecessary interfaces, which should be a good thing in the long term. Some other good news is that there are now weekly IRC meetings of the Opensync developers, so there should be steadier progress towards Opensync-0.40 from now on. Unfortunately, I was mostly absent during all of the three meetings so far. Along with Opensync-0.38, libsyncml saw a new major release 0.5.0 which should fix lots of bugs and provide better support for mobiles. However, lots of problems with syncml were due to bugs in the wbxml2 library. Michael Bell has hopefully found the most critical ones and I have uploaded a new wbxml2-0.9.2 to unstable today which I hope will get into lenny soon. The main problem with wbxml2 over the last year was a unresponsive/MIA upstream; however, recently wbxml2 maintainership got tranferred to the opensync project and moved to its Trac. Michael Bell has been fixing most of the outstanding issues and is currently preparing a 0.10.0 release, so this project should be back on track now.

I have uploaded barry package to Debian some hours ago. It is still waiting for NEW processing, so if you want it you will have to download sources from Debian git repo, and compile the package yourself. It has just been accepted into the archive. Barry is a GPL program that will allow you to charge your Blackberry through the USB port, to make backup copies of your device databases, manage contacts and use your BB as a modem. So if you have a BlackBerry device, you can also enjoy it in Debian. Update 26/10/2008: Barry has just been accepted into the archive, so you can get it in every Sid repository mirror. Thanks!

New QA website I modified qa.debian.org’s stylesheet/template, using the PTS’s stylesheet as a basis. It looks a bit better. The content was also updated, so we should stop receiving totally outdated answers to the “What does the QA team do?” question in NM. Now, who is going to do the same thing with www.debian.org? :-) Closing bugs in removed packages When packages are removed from unstable and testing, their bugs are not necessarly marked as closed, so they can’t be archived. A few days ago, there was about 3300 open bugs filed against removed packages. Thanks to the work of Barry deFreese, Marco Rodrigues and Raphael Geissert, we are now down to ~2500 bugs. If you want to help, just drop in #debian-qa and ask about our scripts/process. (There are some tricky details) DEP #1: NMUs With Bas Wijnen, we finally announced the DEP about NMUs we have been working on. Please join the (currently very quiet) discussion!

Juno was totally worth my time, I gave it 5/5 stars. When having a prospective look at it, it didn’t seem I would enjoy it much, but I decided to trust Movielens on this one, and that payed off. Long story short, Juno is a sixteen year old girl that gets pregnant, and then a very appealing movie happens. Then a slightly questionable (rushed?) end comes, but I enjoyed that part the most. I liked the general tone of the movie, and the two youngsters were adorable. The soundtrack was awesome as well. I loved the song on the opening titles, All I want is you by Barry Louis Polisar (listen here), and the one in the last scene, Anyone else but you from The Moldy Peaches, but performed by the actors themselves. Update (2008-01-16): Mention track titles in the last paragraph. Update 2 (2008-01-16): After listening to the soundtrack today, I can’t but highlight Kimya Dawson’s songs, particularly: Tire Swing, Loose Lips, and Tree Hugger.

Earlier today I sent an announcement to the r-packages list. It describes CRANberries, two simple RSS feeds that summarize both 'new' and 'updated' packages at CRAN, the archive network for R. I cooked this up rather quickly using a few lines of R, a small SQLite db backend and the old Blosxom blog engine. A tip of the hat to Barry Rowlingson who almost immediately suggested to use the lol format instead. The hope is that this proves helpful for keeping tabs on the amazing growth of CRAN (which is now at over one thousand packages) as well as the number of updates to existing packages. The feed(s) can be consumed standalone, or via the brand new Planet R aggregator that Elijah announced today too.

Having spent the better part of two days provisioning my new MacBook Pro’s OS X, Debian, and Windows XP instances, I am keenly aware of how much the Debian distribution’s package management system and its volume of packages have spoiled me. In that two days, the amount of time required to provision Debian was negligible, even though it is configured to completely match my Lifebook’s Debian Sid instance. In fact, the sum total of time to set up Debian, including every application I use, was about 45 minutes of my involvement. Those who know Debian (and Ubuntu, Linspire, Xandros, Mepis, or any other Debian derivative) are coolly nodding their heads, while others are probably thinking I am a lying, biased Linux zealot. It’s no lie; here are the steps I had to take:

• Run the Debian Installer business card image and perform a stock Sid installation, choosing Desktop and Standard System options in the task selection step. If you weren’t wanting to run Sid, the netinstall image would be fine as well.
• Generate a package list on the current Debian installation via # dpkg --get-selections > dpkg-selections.txt
• Copy the package list file to the new installation; I have copied it to my home directory in this example.
• Set the package selections for the new installation via # dpkg --set-selections ~/dpkg-selections.txt
• Run aptitude or synaptic and choose the install action, then go do something else. Thousands, literally thousands of software packages are being installed for you. Everything from your email client to your office suite to your software development tools are being pulled down from package mirrors. In my case, this was over 850MB of compressed package files.
• After the package download, answer any configuration questions aptitude (or synaptic) poses.
• Copy your /home directory contents to the new installation.

Compare that to what it takes with either Mac OS X or Windows XP to get all of your applications installed and configured. Even if you don’t know a thing about Linux or even the more technical side of those operating systems, you can tell from the brevity of that set of steps that the Debian setup is remarkably simple. Now, some will already be keying in their comment posts with exclamations of “Hey! There’s DarwinPorts/Fink/Cygwin!” Yeah, each of those is a nice start; however, they pale in comparison. Fink at least has the robust apt/dpkg foundation, but even it has a relatively meager package selection. I am sure I’ll be writing more on life with Fink and DarwinPorts in the near future. I still don’t have half the stuff installed on XP that I plan to use. I get tired just thinking about the installs. 8^)

So I am perusing the “Latest Headlines” RSS feed in Firefox this morning and notice the word ubuntu. It turns out Bill Clinton used it as a key term in a recent speech to the Labour party conference. The article goes on to discuss the increasing ubiquity of the word’s usage, including the mention of Ubuntu the operating system at the end of the article. And apart from a picture of Clinton at the top of the article, the only other image is of an Ubuntu thong like the ones you can buy off of Caf press.com. Of all the choices, why pick an Ubuntu thong? One person suggested to me that Clinton and a thong was a natural fit. 8^)

From a “Required Skills” section of a recent position description: “Motivated self-staring individual; Team player” Huh.

An updated java-package will hit unstable in the next mirror pulse. Apologies to all for the delay; my discretionary time and that of my sponsors has been rather sparse for some time now. There are at least 9 bug reports addressed in the release. All users who have a JRE or JDK packaged by a previous version of java-package are encouraged to first remove their existing packages and then install an updated one generated by 0.28. Again, sorry for my low level of productivity for Debian, but paying my bills and being a new dad has been quite taxing (albeit rewarding) the past nine months.

I recently had to provision a laptop at my client’s site for my use. Certain third-party applications that are key to managing the technology practice there are Windows-only, but I (am fortunately allowed to) refuse to have a Windows-only machine. They are cool enough to let me shrink the corporate WIndows XP image and set up a Debian sid instance for dual-booting. I took my trusty CD of a recent daily snapshot (the fact that I have been able to use daily snapshots of the Debian Installer ISO for several years with little to no trouble is in itself a huge testimony to the quality of that project’s work) and popped it into the media drive of this rather battered Dell Latitude D600. I had heard at DebConf that the graphical installer was now fully part of the daily snapshots, so on a whim I invoked it with the ‘expertgui’ directive at the boot prompt. Wow. If you haven’t seen this, go and burn an ISO of the daily snapshot for your architecture and boot into it. (I won’t even elaborate on the fact that being able to choose from 11 different architectures is massively impressive.) What a beautiful interface, and how amazingly tasteful as far as look-and-feel. It’s very professional-looking, yet not corporate. There’s a button to capture snapshots of the install screens right there on each screen. It may take a minute or two to adjust to having the right line in the display highlighted before clicking the button to continue in more-complex screens, but the annoyance is neglible. I was thoroughly impressed, so much so that I wiped my backup laptop, a ThinkPad T42, and did a reinstall using the graphical interface. You can still pop over to the other virtual terminals just like in the character-based installer; the graphical interface seems to use the fifth virtual terminal. I just popped out of it to the second via Ctrl + Alt + 2 and was able to mount a USB drive with some firmware I needed. I wiped the T42 so I could run the IBM recovery and get XP back on a small partition. Hey, how else am I going to play Warcraft III? (Seriously, though, if anyone has managed to get Warcraft III to run via an emulator, let’s talk.) I found it a study in contrasts, installing XP and then installing Debian immediately after. The first thing I noticed with XP is how little visibility I have into the install process compared to the Debian installer. I suppose I shouldn’t have to since all these vendors have supposedly ensured (stifling audible laughter here) a smooth installation process for me. However, when something does go wrong, I am pretty much out of luck. Second, I have come to take for granted how quickly you can fully provision an OS instance with Debian’s rich package-management system. The benefits of an awesome package management system are painfully obvious as soon as you have to reinstall Windows or OS X, especially if you are a software developer with a whole litany of tools necessary for your work. A graphical installer was the last major impediment to me recommending Debian to my friends and relatives who are too befuddled by a character-based application or installer. This closes a significant gap in the Debian offering, and I wish to sincerely thank those who have poured so much time into the installer project as a whole and have gone the extra distance to create an interface that reaches out to the less-technically-oriented crowd.

Blog commenter James pointed out to me that the esteemed Mark Pilgrim has recently moved back to Linux for his desktop OS as well. Since Mark’s blog post doesn’t have to be conformed to fit conventions of a major technical publishing site, the style is more conversational. His take on the faux openness of the Mac platform is insightful. My favorite two paragraphs from the entry are the following:

I would like to point out that it is entirely Apple s choice that their operating system does not run on my new Lenovo ThinkCentre. I m not saying it was a bad business decision they are a hardware company, after all but it is particularly galling to realize that if I bought a new Mac, I would be subsidizing the development of an operating system that contains code whose sole purpose is to lock me into a specific hardware platform. I realize that most people don t look at it that way, but there it is.

In many ways, the tale of my switch is more of the same old story. Mac OS X was free enough to keep me using something that was not in my long-term best interest. But as I stood in the Apple store last weekend and drooled over the beautiful, beautiful hardware, all I could think was how much work it would take to twiddle with the default settings, install third-party software, and hide all the commercial tie-ins so I could pretend I was in control of my own computer. Beauty is in the eye of the beholder, and to my eye Apple isn t beautiful anymore. I ve worked around it or ignored it for a long time, but eventually the bough breaks.

Spot on, Mark. I still kick myself for thinking it perfectly normal at one time to have to own a PCMCIA network card just to be able to use WLAN with my Aluminum PowerBooks equipped with “Airport Extreme”. Deciding to “switch back” was almost like realizing I was in this relationship with someone who was taking without giving back, and using manipulative schemes to win my allegiance. Oh yeah, and more Mac zealot whinging in the comments, apparently enough for Mark to have turned off comments on that post.

Every now and then you come across an article or blog entry that makes you exclaim “Yes, I know exactly what you mean!” I try to only do that with my inside-the-head voice. I spotted an entry from chromatic on O’Reilly’s LinuxDevCenter RSS feed this morning on switching back to desktop Linux from Mac OS X. This is an excellent writeup that captures all the reasons I had for moving to Linux on my laptops instead of Mac OS X. Desktop Linux is not for everyone, but neither is OS X. Judging from some of the Mac zealots’ whinging, that’s hard for some folks to accept.

The night started great. Tables arranged in a swirl, happy geeks gathered around a good meal, it was going to be a great formal dinner.

Then came AJ and his megalomania. Well, it was kind of fun at the moment, although I still haven't cooled down after seeing his contribution to the Java in non-free thread. He even compromised himself by showing up hand in hand with Ted Walther.

After that, Ted tried to spoil the dinner, and almost managed to do it. Please people, correct me if I'm wrong as I was a few meters away from the incident and didn't follow everything. It seems the person Ted is calling a "local businesswoman" was a prostitute. As he doesn't want to name people, I'll do it: when learning that, Holger tried to throw Ted out of the building. Unfortunately some people stopped him from doing it. Holger, thanks a lot for having the courage to give this guy what he deserves, and already deserved before the provocation, when most people (including me) just stand still when facing such unbearable behavior.

Of course Ted tried to act as a martyr, as shows his blog entry. Ted, I do hope things won't be "resolved to your satisfaction". And anyway, you won't need to denounce the people who deserve to be awarded instead. Why have you come to Debconf for, anyway? Uploading broken versions of your packages, or writing stupid and provocative blog entries?

Then, the mariachis tried to improve the ambiance but only managed to prevent people from talking to each other. The real fun came from the rain, which fell so hard it entered the building in a magnificent cascade, leaving us eating and walking in a few centimeters of water. Another great moment was the power outage, during which we were lightened by camera flashes.

The food had so much success that I didn't have time to taste more than one dish before everything was wiped out. Still, despite Ted and despite the lack of food, this was a great evening, one of those I won't forget for sure.

I'll upload pictures later, but in the meantime you can have a look at Barry Hawkins' blog.

A Coronation Surreal, just surreal. A Cascade An unbelievable rain came, and eventually overwhelmed the roof and came down the wall like a waterfall. A Calamity Imagine a black square here. The power went out, and we all just rolled with it. It was kind of fun, actually. A Cleanup In the spirit of community, numbers of Debian people collaborated for a quick cleanup.

I was too sick to go on the day trip for DebConf, but staying at the conference location had its benefits. After visiting the doctor and getting a prescription, I headed in to town to get the medicine. I ended up discovering the building known as Ex-Convento, a former Catholic convent next to our conference center. It has a quaint little museum and the local public library. I recommend taking a visit if you’re here for DebConf6; it can be a welcome break for the proceedings. A walkthrough of my visit can be found in my flickr set titled Wednesday in Oaxtepec. I ran into Micah, Matt, and the rest of the HP posse on their way to the market. We had a most enjoyable lunch together, plus a little bit of discussion about the thread on debian-devel in response to the announcement message yesterday.

So it’s finally OK to mention it now; Java has made it explicitly possible (read legal) to distribute the Sun Java JRE/JDK on a GNU/Linux distrubtion. The new license is for Java SE 5 on Linux only, called the Operating System Distribution License for Java, or DLJ for short. You can read the license in text or pdf form. The FAQ for the DLJ is also available in text and pdf. Heck, go through the README for the JRE and JDK while you’re at it. So what does that mean? Well, GNU/Linux distrubtions like Debian can now package a Java runtime environment or Java development kit in their repositories. That was previously not possible due to restrictions present in Java licensing. Users still have to accept the Java SE 5 binary code license that is totally not free and has the same restrictions Java has always had, but this at least makes packaging and supporting Java less painful for distributions. Sun is coordinating the efforts via a java.net project, jdk-distros. This is an unprecedented level of cooperation from Sun with external parties in anything related to Java. I consider myself fortunate to have been a founding member of the project. It has been a pleasant and refreshing experience to meet a few optimistic and forward-thinking people from Sun who have a keen interest in Free Software; a big thanks to Simon Phipps and Tom Marble. I was encouraged that they allowed our contributions to be covered under the MIT license. If you would have told me that a month ago I would have laughed at you. The Debian announcment should be posted on the debian-devel-announce list today. I am sure this will draw both praise and ire from the Debian community. That’s cool, though; the rich diversity is part of what makes it such a vibrant organism.